fix call/delagate call tracking bug #7
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What was wrong?
Related to Issue ethereum#1434
The problem was that CALLCODE and DELEGATECALL operations were not tracking the code_address as the TargetContract in the block access list.
How was it fixed?
The TargetContract should be the address whose code is being executed, not the current contract address. I've added track_address_access calls for the code_address in both callcode() (line 497) and delegatecall() (line 637) functions to properly track these accesses.